Make trailing-slash-on-void-elements message not depend on profile code #76
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We probably want to remove
errorProfileMapand all its related stuff in the tokenizer code, since there’s no evidence it’s used by anybody anywhere in any consumer code except for what’s in the checker code, and there’s no evidence that anybody’s using that feature (which has no associated UI and but instead depends on passing in a query param).Given all that, it seems imprudent to yoke the trailing-slash-on-void-elements message behavior to that likely-to-be-removed
errorProfileMapcode.